Non-disruptively splitting a coordinated timing network

ABSTRACT

A coordinated timing network is dynamically split into a plurality of coordinated timing networks. This split occurs without taking down any of the servers. Each coordinated timing network has its own coordinated timing network identifier (CTN ID), and its own primary time server. Optionally, each coordinated timing network includes a backup time server and an arbiter.

This application is a continuation of co-pending U.S. patent applicationSer. No. 14/920,928, filed Oct. 23, 2015, entitled “NON-DISRUPTIVELYSPLITTING A COORDINATED TIMING NETWORK,” which is hereby incorporatedherein by reference in its entirety.

BACKGROUND

One or more aspects relate, in general, to coordinated timing networks,and in particular, to splitting coordinated timing networks.

A Coordinated Timing Network (CTN) is a network in which multipledistinct computing systems maintain time synchronization to form thecoordinated timing network. Systems in the coordinated timing networkemploy a message based protocol, referred to as a Server Time Protocol(STP), to pass timekeeping information between the systems overexisting, high-speed data links. This enables the time of day (TOD)clocks at each system to be synchronized to the accuracy required intoday's high-end computing systems. Since the protocol makes use oftechnology within a computing system, synchronization accuracy scales astechnology improves. A computing system that provides time to othercomputing systems is referred to as a time server or server herein.

Within a coordinated timing network for STP, there is to be only oneserver acting as the source of time for the network (referred to as theprimary time server). If there is more than one time source, the twosources could diverge leading to a data integrity exposure. Likewise, ifthere is no single server acting as the source of time for the network,the clocks on the multiple servers could drift apart, raising a dataintegrity exposure in that way.

Customers using the Server Time Protocol have encountered situations inwhich the coordinated timing network is to be split into multipleseparate CTNs. However, to accomplish this, one or more of the serversneeds to be brought down. This is very disruptive to the customers'business and usually means a loss of business and revenue.

SUMMARY

Shortcomings of the prior art are overcome and additional advantages areprovided through the provision of a computer program product formanaging coordinated timing networks. The computer program productcomprises a storage medium readable by a processing circuit and storinginstructions for performing a method. The method includes determiningthat a coordinated timing network (CTN) is to be split into a pluralityof coordinated timing networks. The coordinated timing network includesa plurality of servers. Based on determining that the coordinated timingnetwork is to be split, splitting the coordinated timing network intothe plurality of coordinated timing networks, wherein the splitting isperformed non-disruptively in that servers of the coordinated timingnetwork continue processing during the splitting.

Computer-implemented methods and systems relating to one or more aspectsare also described and claimed herein. Further, services relating to oneor more aspects are also described and may be claimed herein.

Additional features and advantages are realized through the techniquesdescribed herein. Other embodiments and aspects are described in detailherein and are considered a part of the claimed aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more aspects are particularly pointed out and distinctly claimedas examples in the claims at the conclusion of the specification. Theforegoing and objects, features, and advantages of one or more aspectsare apparent from the following detailed description taken inconjunction with the accompanying drawings in which:

FIG. 1 depicts one example of a coordinated timing network;

FIG. 2 depicts further details of a coordinated timing network, inaccordance with an aspect of the present invention;

FIG. 3 depicts one embodiment of an indication of splitting acoordinated timing network into a plurality of coordinated timingnetworks, in accordance with an aspect of the present invention;

FIG. 4 depicts one embodiment of logic to split a coordinated timingnetwork into a plurality of coordinated timing networks, in accordancewith an aspect of the present invention;

FIG. 5 depicts one example of a new CTN ID information block used inaccordance with an aspect of the present invention;

FIG. 6 depicts one example of a new stratum-1 configuration informationblock used in accordance with an aspect of the present invention;

FIG. 7 shows a result of splitting a coordinated timing network into aplurality of coordinated timing networks, in accordance with an aspectof the present invention;

FIG. 8 depicts one embodiment of a cloud computing node;

FIG. 9 depicts one embodiment of a cloud computing environment; and

FIG. 10 depicts one example of abstraction model layers.

DETAILED DESCRIPTION

In accordance with one or more aspects, a Coordinated Timing Network(CTN) is split into a plurality of coordinated timing networks. This maybe driven by a number of situations, including, but not limited to,changes internal to a business, or a business spinning off andtransferring a portion of its business to a separate corporation, etc.Previously, customers have split a CTN by reassigning the role of theserver serving as the source of time, shutting down all of the serverswhich will remain a part of the old CTN (or instead, the new CTN), andredefining the identifier of the CTN (CTN ID) for the remaining serversto a new CTN ID. The servers which had been shut down can then bebrought up using the old CTN ID, which is separate and independent fromthe new CTN. This process of bringing down the servers to split a CTNinto multiple CTNs is costly and inefficient.

Thus, in accordance with an aspect of the present invention, acoordinated timing network splitting capability is provided that enablesa CTN split to be carried out dynamically, without shutting down any ofthe servers. In one embodiment, particular configuration information isselectively loaded onto certain servers, and an activation step isrecognized only by those servers which have received that information.This allows the CTN split to take place dynamically within a matter ofseconds without requiring the customer to shut down any of the servers.This represents a significant savings both in time and effort by thecustomer in addition to not requiring the temporary loss of anymachines.

One embodiment of a coordinated timing network is described withreference to FIG. 1. In this example, a coordinated timing network 100includes a plurality of servers 102 coupled to one another via one ormore STP links 104. For example, the plurality of servers 102 includesServer A 102 a and Server B 102 b. Although in this example, two serversare depicted, coordinated timing network 100 may include additionalservers. Each server is coupled to a support element 106, which isfurther coupled to a hardware management console 108. The hardwaremanagement console may be the same console or a different console foreach support element.

As examples, each server is a central electronics complex based on thez/Architecture offered by International Business Machines Corporation(IBM); the hardware management console is, for instance, a personalcomputer, such as an Intel-based personal computer with a DVD-RAM(digital video disk-random access memory), as a particular example, orother type of computer or processing device that includes functionalityto provide a standard interface for configuring and operatingpartitioned and SMP (Symmetric Multiprocessing) systems, such as Systemz offered by International Business Machines Corporation; and eachsupport element is, for instance, a workstation coupled to the centralprocessing complex used for monitoring and operating a system. Examplehardware management consoles and support elements are based ontechnology offered by International Business Machines Corporation.z/Architecture is a registered trademark of International BusinessMachines Corporation, Armonk, N.Y., USA. One embodiment of thez/Architecture is described in “z/Architecture Principles of Operation,”IBM Publication No. SA22-7832-10, March 2015, which is herebyincorporated herein by reference in its entirety.

Further details regarding coordinated timing network 100 are describedwith reference to FIG. 2. In this example, coordinated timing network100 includes a plurality of servers 102 (e.g., servers 102 a-102 f), andeach server 102 includes one or more partitions 200 (e.g., logicalpartitions). Each partition is part of a particular Sysplex (systemcomplex of servers), and the Sysplex of a particular partition isindicated by the letter A or B, in this example. Thus, partitions 200 aare part of Sysplex A, and partitions 200 b are part of Sysplex B.

Further, in one example, one of the servers, server 102 a, is a primarytime server (PTS) 210 providing current time for coordinated timingnetwork 100. Further, server 102 d is a backup time server (BTS) 212 forcoordinated timing network 100. Yet further, another server 102 c is anarbiter (ARB) 214 for coordinated timing network 100. The arbiter serverfacilitates determination of a failure of the primary time server. Asshown in FIG. 2, each server is part of a single coordinated timingnetwork as indicated by a CTN ID 250 (e.g., CTN ID 1) in each server102.

Although certain servers are indicated as providing the timing roles ofprimary time server, backup time server and arbiter, in one embodiment,these roles are provided by the servers in conjunction with theirsupport elements.

Servers in a CTN that are in the synchronized state are assigned avalue, referred to as a stratum level, that specifies the number ofservers between it and a primary time server. A primary time serveroperates at a stratum level of 1; secondary time servers operate at astratum level of 2 or above, which increases as the number of servers inthe timing path to the stratum-1 increases. In general, the quality oftimekeeping information decreases as the stratum level increases. Aserver that is unsynchronized is assigned a stratum level of 0.

In one example, a customer would like to split the CTN into multiplecoordinated timing networks. For instance, CTN 100 is to be split intotwo coordinated timing networks, as indicated in FIG. 3 at 300. In thisexample, servers 102 a-102 c are to be a part of a first coordinatedtiming network 302 a, also referred to herein as the “old” coordinatedtiming network; and servers 102 d-102 f are to be a part of a secondcoordinated timing network 302 b, referred to herein as a “new”coordinated timing network. In one example, if a coordinated timingnetwork is to be split, then all partitions of one Sysplex are to be apart of the same coordinated timing network. For instance, in theparticular example of FIG. 3, the partitions of Sysplex A are to be apart of coordinated timing network 302 a, and the partitions of SysplexB are to be a part of coordinated timing network 302 b. Thus, thepartition of Sysplex A (200 a) located in server 102 f is to be moved toone of servers 102 a-102 c, as described further below.

One embodiment of logic used to split a coordinated timing network intomultiple timing networks is described with reference to FIG. 4. In oneexample, one or more processors of one or more support elements and/orone or more servers are used to perform aspects of the logic to splitthe coordinated timing network.

Referring to FIG. 4, initially, any partitions of a sysplex to be a partof the old CTN that are currently in a server that is to be included inthe new CTN (e.g., partition 200 a of server 102 f) are migrated to aserver of the old CTN, STEP 400. For instance, partition 200 a of server102 f is to be moved to any of servers 102 a-102 c. In this particularexample, it is moved to server 102 b, as shown in FIG. 7 at reference702, discussed further below. This includes, for instance, an operatoraction to shift the configuration to move the image of the sysplex.

Further, if any server that is to be included in the new CTN has atiming role, such as a primary time server, a backup time server or anarbiter, then that role is migrated to a server in the old CTN, STEP401. For instance, the backup time server role is currently in a serverthat is to be included in the new CTN, thus, the role of the backup timeserver is migrated from its current server (e.g., server 102 d) to oneof the servers to be included in the old CTN (e.g., server 102 b). Thisincludes, for instance, selecting by the operator, via, e.g., an STPcontrol panel on the support element coupled to the primary time server,a new server (e.g., server 102 b) to take on the role of the backup timeserver. This selection results in a command, such as a modify stratum-1configuration command, to be sent from the support element (or inanother example, from a server, such as server 102 a) to the servers ofthe CTN that indicates the change in the timing roles. The modifystratum-1 configuration command includes in its request block a newstratum-1 configuration information block or at least an indication ofthe block that provides the configuration information, including the newtiming roles, as described below.

Additionally, a new CTN ID information block is sent to each server thatis to be included in the new coordinated timing network, STEP 402. Thisblock provides an identifier of the new coordinated timing network tothe servers that are to belong to that CTN. It also provides a set splitindicator that indicates that a split is to be performed, and thus,activation of the new CTN ID is not to be performed immediately, butinstead, after receipt of a modify stratum-1 configuration command to besent shortly. In particular, in one example, a modify CTN ID command isissued by the operator at a support element of each server to beincluded in the new CTN (e.g., servers 102 d-102 f) and each supportelement then provides the command to its corresponding server. Thecommand includes in its request block the new CTN ID information blockor at least an indication of the block, and that block providesparticular information to the servers of the new CTN.

One example of a new CTN ID information block is described withreference to FIG. 5. As one example, a new CTN ID information block 500includes, for instance, a new CTN ID 502 identifying the new CTN; asplit indicator 504 (e.g., a bit), which when one, indicates that theserver will become a member of the new CTN—this data will not be actedupon until a stratum-1 configuration is activated that has a matchingCTN ID, as described below; an ETR (external time reference) Port 0Manual Port State (port 0 state) 506 that includes a manual port statecode that specifies the intended state of ETR port 0, when the new CTNID field specifies a non-null ETR network number; an ETR Port 1 ManualPort State (port 1 state) 508 that includes a manual port state codethat specifies the intended state of ETR port 1, when the new CTN IDfield specifies a non-null ETR network number; and a new CTN update time510 providing a time in which the new CTN is to become current (Note:This field is ignored when split indicator 504 is set.). Althoughvarious fields are described herein, more, less and/or different fieldsmay be included in the new CTN ID information block without departingfrom a spirit of one or more aspects of the present invention.

Returning to FIG. 4, in addition to sending the new CTN ID informationblock, a new configuration (e.g., a new stratum-1 configuration) is sentto the server designated to be the new primary time server for the newcoordinated timing network (e.g., server 102 d), STEP 404. In oneexample, a modify stratum-1 configuration command is issued at thesupport element coupled to the server designated to be the new primarytime server, and that support element provides the command to thatserver. A request block of the command includes, for instance, a newstratum-1 configuration information block or at least an indication ofthe block, and that block includes configuration information.

One embodiment of a new stratum-1 configuration information block isdescribed with reference to FIG. 6. In one example, a new stratum-1configuration information block 600 includes a plurality of fields thatinclude information, such as, for instance:

-   -   A primary stratum-1 node descriptor 602: This field is valid        when a single server, dual server or triad definition has been        specified in the configuration type field (discussed below) and        includes the node descriptor of the new primary stratum-1 node;    -   An alternate stratum-1 node descriptor 604: This field is valid        when a dual server or triad definition has been specified in the        configuration type field and includes the node descriptor of the        new alternate stratum-1 node (i.e., the backup time server);    -   An optional arbiter node descriptor 606: This field is valid        when a triad definition has been specified in the configuration        type field and includes the node descriptor of the new arbiter        node;    -   A stratum-1 configuration update time 608: This field includes a        timestamp that indicates when the values in this block are to        become current for the CTN;    -   A configuration type 610: This field specifies the type of        stratum-1 configuration, as defined below:        -   Null definition—None of the node descriptors are valid.        -   Single server definition—Only the primary stratum-1 node            descriptor is valid. In a single server configuration, if            the primary time server is lost, synchronized time for the            CTN is lost, since there is no backup.        -   Dual server definition—The primary stratum-1 and alternate            stratum-1 (backup time server) node descriptors are valid.            In a dual server configuration, a mechanism is provided for            an alternate server to be able to take over the role of an            active stratum-1 server for the CTN.        -   Triad definition—The primary stratum-1, alternate stratum-1            and arbiter node descriptors are valid. In a triad            configuration, a primary time server, a backup time server            and an arbiter are provided. The arbiter server may be used            to determine a failure of the primary time server.    -   A split indicator 612: When the split indicator (e.g., a bit) is        set to one, it indicates that this is a special configuration        that will be used to split the CTN into multiple coordinated        timing networks. When this configuration is activated, if a        server has a matching new CTN ID with its own split bit set, it        will activate the new CTN ID as well as the stratum-1        configuration. If a server does not have a matching new CTN ID        or if the split bit is not set, it will not activate this        configuration, simply throwing the configuration away, and        clearing out both the new CTN ID and new stratum-1 configuration        blocks; and    -   A new CTN ID 614: This field specifies a new CTN identifier        identifying the new CTN.

Although various fields are described herein, more, less and/ordifferent fields may be included in the new stratum-1 configurationinformation block without departing from a spirit of one or more aspectsof the present invention.

Returning to FIG. 4, the new primary time server (e.g., the supportelement and/or server) sends the new stratum-1 configuration to thecurrent primary time server, STEP 406. The current primary time server(e.g., the support element and/or server) then sends the new stratum-1configuration to all servers in the coordinated timing network, STEP408. In one example, the new configuration is sent via the modifystratum-1 configuration command. This command includes the new stratum-1configuration information block or an indication of the configurationblock in a request block of the command. This request block may furtherindicate this is a requested split reconfiguration.

Each server, based on receiving the new stratum-1 configuration and therequested split reconfiguration, checks its local split indicator to seeif the server is to be a part of the new coordinated timing network,STEP 410. That is, each server checks its configuration area todetermine whether it received a new CTN ID information block with a setsplit indicator 504 (e.g., set to 1). If its indicator is set, INQUIRY412, then the new CTN ID is set and the new configuration is activatedat that server, STEP 414. In one example, this includes indicating thenew stratum-1 configuration is to be recognized, based on reaching thestratum-1 configuration update time. Additionally, all of the STPconnections for the servers in the new CTN are restarted (e.g., bysending new connection requests). The servers remaining in the old CTNwill not connect because the CTN IDs do not match. Therefore, STPconnections after the split may only exist between servers which arepart of the same CTN.

Returning to INQUIRY 412, if the split indicator is not set for aparticular server, then the command is ignored by that server, STEP 416.This allows the coordinated timing network to be split non-disruptivelyin that none of the servers need to be taken off-line. That is, eachserver may continue processing its workload.

A resulting split coordinated timing network is depicted in FIG. 7. Asshown, servers 102 a-102 c are in one coordinated timing network 710 ahaving a coordinated timing network ID of 1 (700 a); and servers 102d-102 f are in the new coordinated timing network 710 b as identified bya CNT ID of 2 (700 b). Each coordinated timing network in this examplehas a primary time server (PTS), a backup time server (BTS) and anarbiter (ARB).

In one further embodiment, the coupling links between the two CTNs maybe removed as well.

Described in detail herein is a CTN splitting capability that changesthe CTN ID for one or more servers of a CTN and concurrently changeswhich server is to be the source of time for the CTN without shuttingdown any of the servers. Although it is indicated herein that serversperform or are involved in certain actions, these actions may beperformed by the servers, the support elements coupled to the serversand/or by a combination of the servers and the support elements. Thus,the term “component of a server” used herein may include the server, thesupport element and/or the server with the support element.

As described herein, in one or more aspects, a configuration change isloaded onto each of the servers which will become a part of the newcoordinated timing network (via, e.g., standard STP operating commands).This new configurations includes a special flag (e.g., the splitindicator) to indicate this is part of a split CTN change, a new CTN ID,as well as the definition of the source of time roles for the new CTN.These changes remain dormant until specifically activated. Once all ofthe new configurations have been loaded and the customer is ready tomake the change, an STP operating command, such as a modify stratum-1configuration command, is sent throughout the entire current unsplit CTNwith a flag indicating this is a split CTN situation. Upon receipt ofthis command, each server checks its configuration area to see if thesplit indicator has been set locally (via a new configuration). If it isset, then the new configuration is activated; otherwise, the command isignored. As with any configuration change for STP, the STP connectionsare restarted to ensure that the configurations match. In the splitsituation, the STP connections after the split only remain betweenservers which are part of the same CTN, so the CTN will have beeneffectively split.

One or more aspects may relate to cloud computing.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forloadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 8, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 8, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 9, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 9 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 10, a set of functional abstraction layersprovided by cloud computing environment 50 (FIG. 9) is shown. It shouldbe understood in advance that the components, layers, and functionsshown in FIG. 10 are intended to be illustrative only and embodiments ofthe invention are not limited thereto. As depicted, the following layersand corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and split processing 96.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

In addition to the above, one or more aspects may be provided, offered,deployed, managed, serviced, etc. by a service provider who offersmanagement of customer environments. For instance, the service providercan create, maintain, support, etc. computer code and/or a computerinfrastructure that performs one or more aspects for one or morecustomers. In return, the service provider may receive payment from thecustomer under a subscription and/or fee agreement, as examples.Additionally or alternatively, the service provider may receive paymentfrom the sale of advertising content to one or more third parties.

In one aspect, an application may be deployed for performing one or moreembodiments. As one example, the deploying of an application comprisesproviding computer infrastructure operable to perform one or moreembodiments.

As a further aspect, a computing infrastructure may be deployedcomprising integrating computer readable code into a computing system,in which the code in combination with the computing system is capable ofperforming one or more embodiments.

As yet a further aspect, a process for integrating computinginfrastructure comprising integrating computer readable code into acomputer system may be provided. The computer system comprises acomputer readable medium, in which the computer medium comprises one ormore embodiments. The code in combination with the computer system iscapable of performing one or more embodiments.

Although various embodiments are described above, these are onlyexamples. For example, computing environments of other architectures canbe used to incorporate and use one or more embodiments. Further,different instructions, instruction formats, instruction fields and/orinstruction values may be used. Many variations are possible.

Further, other types of computing environments can benefit and be used.As an example, a data processing system suitable for storing and/orexecuting program code is usable that includes at least two processorscoupled directly or indirectly to memory elements through a system bus.The memory elements include, for instance, local memory employed duringactual execution of the program code, bulk storage, and cache memorywhich provide temporary storage of at least some program code in orderto reduce the number of times code must be retrieved from bulk storageduring execution.

Input/Output or I/O devices (including, but not limited to, keyboards,displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives andother memory media, etc.) can be coupled to the system either directlyor through intervening I/O controllers. Network adapters may also becoupled to the system to enable the data processing system to becomecoupled to other data processing systems or remote printers or storagedevices through intervening private or public networks. Modems, cablemodems, and Ethernet cards are just a few of the available types ofnetwork adapters.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used herein, thesingular forms “a”, “an” and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willbe further understood that the terms “comprises” and/or “comprising”,when used in this specification, specify the presence of statedfeatures, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, steps, operations, elements, components and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below, if any, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of one or more embodiments has been presentedfor purposes of illustration and description, but is not intended to beexhaustive or limited to in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain variousaspects and the practical application, and to enable others of ordinaryskill in the art to understand various embodiments with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A computer program product for managingcoordinated timing networks, the computer program product comprising: acomputer readable storage medium readable by a processing circuit andstoring instructions for performing a method comprising: determiningthat a coordinated timing network (CTN) is to be split into a pluralityof coordinated timing networks, the coordinated timing network includinga plurality of servers; and based on determining that the coordinatedtiming network is to be split, splitting the coordinated timing networkinto the plurality of coordinated timing networks, wherein the splittingis performed non-disruptively in that servers of the coordinated timingnetwork continue processing during the splitting.
 2. The computerprogram product of claim 1, wherein the plurality of coordinated timingnetworks comprises one coordinated timing network and anothercoordinated timing network, and wherein the one coordinated timingnetwork comprises one set of servers of the plurality of servers and theother coordinated timing network comprises another set of servers of theplurality of servers.
 3. The computer program product of claim 2,wherein the splitting comprises: providing a new CTN identifier to theother set of servers to be included in the other coordinated timingnetwork; and providing a new configuration to the plurality of serversin the coordinated timing network, the new configuration employed toindicate which servers of the CTN are to be a part of the one set ofservers and which servers of the CTN are to be a part of the other setof servers.
 4. The computer program product of claim 3, wherein theproviding the new CTN identifier further includes providing a splitindicator set to indicate that the other set of servers is to beincluded in the other coordinated timing network.
 5. The computerprogram product of claim 4, wherein the providing the new CTN identifiercomprises providing a new CTN identifier information block, the new CTNidentifier information block comprising the new CTN identifier and thesplit indicator.
 6. The computer program product of claim 3, wherein theproviding the new configuration comprises: providing the newconfiguration to a server of the other set of servers designated to be aprimary time server of the other coordinated timing network; andproviding by the primary time server of the other coordinated timingnetwork, the new configuration to a primary time server of the onecoordinated timing network, the primary time server of the onecoordinated timing network to provide the new configuration to theplurality of servers in the coordinated timing network.
 7. The computerprogram product of claim 6, wherein the method further comprises:receiving by a component of a server of the other set of servers the newconfiguration; checking by the component of the server of the other setof servers a split indicator; and based on determining the splitindicator is set, activating the new configuration by the component ofthe server of the other set of servers.
 8. The computer program productof claim 3, wherein the providing the new configuration comprisesproviding a new configuration block that includes the new configuration.9. The computer program product of claim 3, wherein the newconfiguration includes an indication of which server of the other set ofservers is to be a primary time server.
 10. The computer program productof claim 9, wherein the new configuration further includes anotherindication of which other server of the other set of servers is to be abackup time server.
 11. A computer system for managing coordinatedtiming networks, the computer system comprising: a memory; and aprocessor in communication with the memory, wherein the computer systemis configured to perform a method, said method comprising: determiningthat a coordinated timing network (CTN) is to be split into a pluralityof coordinated timing networks, the coordinated timing network includinga plurality of servers; and based on determining that the coordinatedtiming network is to be split, splitting the coordinated timing networkinto the plurality of coordinated timing networks, wherein the splittingis performed non-disruptively in that servers of the coordinated timingnetwork continue processing during the splitting.
 12. The computersystem of claim 11, wherein the plurality of coordinated timing networkscomprises one coordinated timing network and another coordinated timingnetwork, and wherein the one coordinated timing network comprises oneset of servers of the plurality of servers and the other coordinatedtiming network comprises another set of servers of the plurality ofservers.
 13. The computer system of claim 12, wherein the splittingcomprises: providing a new CTN identifier and a split indicator to theother set of servers to be included in the other coordinated timingnetwork, the split indicator set to indicate that the other set ofservers is to be included in the other coordinated timing network; andproviding a new configuration to the plurality of servers in thecoordinated timing network, the new configuration employed to indicatewhich servers of the CTN are to be a part of the one set of servers andwhich servers of the CTN are to be a part of the other set of servers.14. The computer system of claim 13, wherein the providing the newconfiguration comprises: providing the new configuration to a server ofthe other set of servers designated to be a primary time server of theother coordinated timing network; and providing by the primary timeserver of the other coordinated timing network, the new configuration toa primary time server of the one coordinated timing network, the primarytime server of the one coordinated timing network to provide the newconfiguration to the plurality of servers in the coordinated timingnetwork.
 15. The computer program product of claim 14, wherein themethod further comprises: receiving by a component of a server of theother set of servers the new configuration; checking by the component ofthe server of the other set of servers the split indicator; and based ondetermining the split indicator is set, activating the new configurationby the component of the server of the other set of servers.
 16. Acomputer-implemented method of managing coordinated timing networks, thecomputer-implemented method comprising: determining that a coordinatedtiming network (CTN) is to be split into a plurality of coordinatedtiming networks, the coordinated timing network including a plurality ofservers; and based on determining that the coordinated timing network isto be split, splitting the coordinated timing network into the pluralityof coordinated timing networks, wherein the splitting is performednon-disruptively in that servers of the coordinated timing networkcontinue processing during the splitting.
 17. The computer-implementedmethod of claim 16, wherein the plurality of coordinated timing networkscomprises one coordinated timing network and another coordinated timingnetwork, and wherein the one coordinated timing network comprises oneset of servers of the plurality of servers and the other coordinatedtiming network comprises another set of servers of the plurality ofservers.
 18. The computer-implemented method of claim 17, wherein thesplitting comprises: providing a new CTN identifier and a splitindicator to the other set of servers to be included in the othercoordinated timing network, the split indicator set to indicate that theother set of servers is to be included in the other coordinated timingnetwork; and providing a new configuration to the plurality of serversin the coordinated timing network, the new configuration employed toindicate which servers of the CTN are to be a part of the one set ofservers and which servers of the CTN are to be a part of the other setof servers.
 19. The computer-implemented method of claim 18, wherein theproviding the new configuration comprises: providing the newconfiguration to a server of the other set of servers designated to be aprimary time server of the other coordinated timing network; andproviding by the primary time server of the other coordinated timingnetwork, the new configuration to a primary time server of the onecoordinated timing network, the primary time server of the onecoordinated timing network to provide the new configuration to theplurality of servers in the coordinated timing network.
 20. Thecomputer-implemented method of claim 19, further comprising: receivingby a component of a server of the other set of servers the newconfiguration; checking by the component of the server of the other setof servers the split indicator; and based on determining the splitindicator is set, activating the new configuration by the component ofthe server of the other set of servers.